Skip to main content

What is software quality? Explain different attributes of software quality.

Software Quality: Definition and Importance​

Software quality refers to the degree to which a software product meets specified requirements, satisfies user needs, and adheres to established standards and best practices. It encompasses both functional and non-functional aspects of software and represents the overall value that the software provides to its stakeholders.

According to the IEEE Standard Glossary of Software Engineering Terminology (IEEE 610.12-1990), software quality is defined as:

  1. The degree to which a system, component, or process meets specified requirements
  2. The degree to which a system, component, or process meets customer or user needs or expectations

Software quality is critical because it:

  • Determines user satisfaction and adoption
  • Affects business reputation and success
  • Impacts maintenance costs and long-term viability
  • Influences security, safety, and regulatory compliance
  • Affects development efficiency and project success

Software Quality Models​

Several models have been developed to define and measure software quality systematically. The most prominent ones include:

1. McCall's Quality Model (1977)​

Organizes quality factors into three perspectives:

  • Product Operation (how well it works)
  • Product Revision (how easy it is to change)
  • Product Transition (how adaptable it is)

2. Boehm's Quality Model (1978)​

Focuses on utility (how useful the software is) and maintainability (how easy it is to understand, modify, and test).

3. ISO/IEC 9126 (Later evolved into ISO/IEC 25010)​

A comprehensive model that defined six main characteristics, each with multiple sub-characteristics.

4. ISO/IEC 25010:2011 (Current Standard)​

The most widely recognized modern quality model, defining eight primary quality characteristics with multiple sub-characteristics.

Software Quality Attributes​

The following are the key attributes of software quality based primarily on the ISO/IEC 25010 model, with some additions from other important quality frameworks:

1. Functional Suitability​

Functional suitability refers to the degree to which a software product provides functions that meet stated and implied needs when used under specified conditions.

Sub-attributes:

a. Functional Completeness​

The degree to which the set of functions covers all specified tasks and user objectives.

Example: A word processing application should include all essential functions like text editing, formatting, spell checking, and printing.

Measurement:

  • Percentage of functional requirements implemented
  • Ratio of missing functions to required functions

b. Functional Correctness​

The degree to which a product provides the correct results with the needed degree of precision.

Example: A banking application must calculate interest rates with the correct precision and according to the specified formulas.

Measurement:

  • Number of computational errors
  • Calculation accuracy rate

c. Functional Appropriateness​

The degree to which the functions facilitate the accomplishment of specified tasks and objectives.

Example: A mobile food delivery app providing streamlined ordering process without unnecessary steps.

Measurement:

  • Task completion rates
  • Number of steps to complete core functions

2. Performance Efficiency​

Performance efficiency relates to the amount of resources used and the performance level under stated conditions.

Sub-attributes:

a. Time Behavior​

The degree to which the response and processing times and throughput rates of a product meet requirements.

Example: A web page loading within 2 seconds, or a transaction processing system handling 1000 transactions per second.

Measurement:

  • Response time
  • Throughput rate
  • Latency

b. Resource Utilization​

The degree to which the amounts and types of resources used by a product meet requirements.

Example: A mobile application using minimal battery power and memory.

Measurement:

  • CPU usage
  • Memory consumption
  • Battery usage
  • Network bandwidth consumption

c. Capacity​

The degree to which the maximum limits of a product parameter meet requirements.

Example: A database system able to handle 10,000 concurrent users or store 10 TB of data.

Measurement:

  • Maximum number of concurrent users
  • Maximum data storage
  • Maximum transaction volume

3. Compatibility​

Compatibility is the degree to which a product can exchange information with other products, systems, or components, and/or perform its required functions while sharing the same hardware or software environment.

Sub-attributes:

a. Co-existence​

The degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact.

Example: Multiple applications running simultaneously on a computer without conflicts.

Measurement:

  • Resource conflicts when running with other applications
  • Performance degradation in shared environments

b. Interoperability​

The degree to which two or more systems, products, or components can exchange information and use the information that has been exchanged.

Example: A healthcare system exchanging patient data with laboratory systems using standard formats like HL7.

Measurement:

  • Number of successful data exchanges
  • Compliance with industry standards

4. Usability​

Usability is the degree to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.

Sub-attributes:

a. Appropriateness Recognizability​

The degree to which users can recognize whether a product is appropriate for their needs.

Example: Clear product descriptions and previews that help users understand what the software does.

Measurement:

  • Time to identify appropriate features
  • Accuracy of user expectations

b. Learnability​

The degree to which a product can be used by specified users to achieve specified goals of learning to use the product.

Example: An intuitive interface with progressive disclosure of advanced features.

Measurement:

  • Time to learn basic tasks
  • Learning curve metrics

c. Operability​

The degree to which a product has attributes that make it easy to operate and control.

Example: Consistent navigation, clear feedback, and undo/redo capabilities.

Measurement:

  • Task completion rates
  • Error rates during operation

d. User Error Protection​

The degree to which a system protects users against making errors.

Example: Confirmation dialogs for destructive actions and input validation.

Measurement:

  • Number of user errors
  • Recovery rate from errors

e. User Interface Aesthetics​

The degree to which a user interface enables pleasing and satisfying interaction for the user.

Example: Visually appealing design with consistent styling and proper spacing.

Measurement:

  • User satisfaction ratings
  • Aesthetic evaluation scores

f. Accessibility​

The degree to which a product can be used by people with the widest range of characteristics and capabilities.

Example: Supporting screen readers, keyboard navigation, and adjustable text sizes.

Measurement:

  • Compliance with accessibility standards (e.g., WCAG)
  • Usability tests with diverse user groups

5. Reliability​

Reliability is the degree to which a system, product, or component performs specified functions under specified conditions for a specified period.

Sub-attributes:

a. Maturity​

The degree to which a system meets needs for reliability under normal operation.

Example: A system that operates consistently without unexpected failures during regular use.

Measurement:

  • Mean Time Between Failures (MTBF)
  • Failure rate

b. Availability​

The degree to which a system, product, or component is operational and accessible when required for use.

Example: A cloud service with 99.99% uptime.

Measurement:

  • Uptime percentage
  • Service availability

c. Fault Tolerance​

The degree to which a system operates as intended despite the presence of hardware or software faults.

Example: A system that continues to function when a component fails, perhaps with degraded performance.

Measurement:

  • Percentage of faults handled without system failure
  • Recovery success rate

d. Recoverability​

The degree to which a product can recover data and re-establish the desired state in case of an interruption or a failure.

Example: A document editor that auto-saves work and can recover after a crash.

Measurement:

  • Recovery time
  • Data loss frequency

6. Security​

Security is the degree to which a product or system protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization.

Sub-attributes:

a. Confidentiality​

The degree to which a product ensures that data are accessible only to those authorized to have access.

Example: Encryption of sensitive data and proper access controls.

Measurement:

  • Encryption strength
  • Security vulnerability counts related to unauthorized access

b. Integrity​

The degree to which a system, product, or component prevents unauthorized modification of data.

Example: Checksums to verify data hasn't been tampered with and audit logs of changes.

Measurement:

  • Data corruption incidents
  • Unauthorized modification attempts detected

c. Non-repudiation​

The degree to which actions or events can be proven to have taken place so that the events or actions cannot be repudiated later.

Example: Digital signatures for transactions and comprehensive audit logs.

Measurement:

  • Strength of non-repudiation mechanisms
  • Disputes related to action attribution

d. Accountability​

The degree to which the actions of an entity can be traced uniquely to the entity.

Example: Detailed user activity logs and user-specific credentials.

Measurement:

  • Completeness of audit trails
  • Accuracy of user attribution

e. Authenticity​

The degree to which the identity of a subject or resource can be proved to be the one claimed.

Example: Multi-factor authentication and identity verification processes.

Measurement:

  • Authentication mechanism strength
  • Authentication bypass incidents

7. Maintainability​

Maintainability is the degree of effectiveness and efficiency with which a product or system can be modified to improve it, correct it, or adapt it to changes in environment and requirements.

Sub-attributes:

a. Modularity​

The degree to which a system is composed of discrete components such that a change to one component has minimal impact on other components.

Example: A system designed with well-defined interfaces between components.

Measurement:

  • Coupling metrics
  • Impact analysis of changes

b. Reusability​

The degree to which an asset can be used in more than one system, or in building other assets.

Example: Generic utilities and components that can be shared across applications.

Measurement:

  • Code reuse percentage
  • Number of reused components

c. Analyzability​

The degree of effectiveness and efficiency with which it is possible to assess the impact of an intended change to one or more parts of a system.

Example: Well-documented code with clear dependencies.

Measurement:

  • Time to identify the cause of a failure
  • Effort required for code understanding

d. Modifiability​

The degree to which a product can be effectively and efficiently modified without introducing defects or degrading quality.

Example: Clean code design that facilitates changes with minimal side effects.

Measurement:

  • Change success rate
  • Effort required for modifications

e. Testability​

The degree of effectiveness and efficiency with which test criteria can be established for a system and tests can be performed to determine whether those criteria have been met.

Example: Code designed with dependency injection to facilitate unit testing.

Measurement:

  • Test coverage
  • Time required to implement tests

8. Portability​

Portability is the degree of effectiveness and efficiency with which a system, product, or component can be transferred from one hardware, software or other operational or usage environment to another.

Sub-attributes:

a. Adaptability​

The degree to which a product can effectively and efficiently be adapted for different or evolving hardware, software, or other operational or usage environments.

Example: A system designed to work across different operating systems or database platforms.

Measurement:

  • Number of supported platforms
  • Effort required for adaptation

b. Installability​

The degree of effectiveness and efficiency with which a product can be successfully installed and/or uninstalled in a specified environment.

Example: A software package with a streamlined installation wizard.

Measurement:

  • Installation success rate
  • Installation time

c. Replaceability​

The degree to which a product can replace another specified software product for the same purpose in the same environment.

Example: A new system designed to be a drop-in replacement for a legacy system.

Measurement:

  • Migration success rate
  • Compatibility with existing interfaces

9. Additional Quality Attributes​

Beyond the ISO/IEC 25010 model, several other important quality attributes are often considered:

a. Scalability​

The ability of a system to handle a growing amount of work by adding resources to the system.

Example: A web application that can be scaled horizontally by adding more servers.

Measurement:

  • Performance under increased load
  • Resource requirements for scaling

b. Flexibility​

The ease with which a system can be modified for use in applications or environments other than those for which it was specifically designed.

Example: A system with configurable workflows and business rules.

Measurement:

  • Range of supported configurations
  • Effort required for customization

c. Supportability​

The ability of the system to provide information helpful for identifying and resolving issues.

Example: Comprehensive logging, diagnostics, and troubleshooting tools.

Measurement:

  • Mean Time To Repair (MTTR)
  • Support ticket resolution time

d. Time to Market​

The ability to develop and deploy software quickly to meet business needs.

Example: A system built using rapid development frameworks and CI/CD pipelines.

Measurement:

  • Development cycle time
  • Feature delivery rate

e. Sustainability​

The degree to which a software system's long-term use is economically viable and socially responsible.

Example: Energy-efficient algorithms and ethical data practices.

Measurement:

  • Energy consumption
  • Environmental impact
  • Ethical compliance

Measuring Software Quality​

Software quality can be measured through various approaches:

1. Metrics-Based Measurement​

Using specific metrics for each quality attribute, such as:

  • Defect density: Number of defects per thousand lines of code
  • Code coverage: Percentage of code executed by tests
  • Cyclomatic complexity: Measure of code complexity based on control flow
  • Response time: Time taken to respond to a user action
  • Mean Time Between Failures (MTBF): Average time between system failures

2. Quality Models and Standards​

Using established models and standards to assess quality:

  • ISO/IEC 25010: Product quality model
  • CISQ: Consortium for IT Software Quality
  • CMM/CMMI: Capability Maturity Model (Integration)
  • ISO 9001: Quality management systems

3. User-Based Assessment​

Gathering feedback from actual users:

  • User satisfaction surveys
  • Usability testing
  • Customer feedback analysis
  • App store ratings and reviews

4. Review-Based Measurement​

Systematic evaluation by experts:

  • Code reviews
  • Architecture reviews
  • Security audits
  • Heuristic evaluations

Quality Assurance vs. Quality Control​

Two complementary approaches to ensuring software quality:

Quality Assurance (QA)​

A proactive process focused on preventing defects through proper planning, monitoring, and improving the development process.

Activities:

  • Establishing quality standards and procedures
  • Process improvement
  • Training and mentoring
  • Defining test strategies
  • Setting up development environments

Quality Control (QC)​

A reactive process focused on identifying defects in existing products through various testing and review activities.

Activities:

  • Various testing types (unit, integration, system, etc.)
  • Code reviews
  • Defect tracking and resolution
  • Validation against requirements
  • User acceptance testing
┌─────────────────────────────────────────────────┐
│                                                 │
│               Software Quality                  │
│                                                 │
├───────────────────────┬─────────────────────────┤
│                       │                         │
│   Quality Assurance   │   Quality Control       │
│   (Process-focused)   │   (Product-focused)     │
│                       │                         │
├───────────────────────┼─────────────────────────┤
│                       │                         │
│ • Process design      │ • Testing               │
│ • Standards setting   │ • Inspection            │
│ • Training            │ • Review                │
│ • Prevention          │ • Detection             │
│ • Proactive           │ • Reactive              │
│                       │                         │
└───────────────────────┴─────────────────────────┘

Strategies for Improving Software Quality​

1. Process-Level Strategies​

  • Adopting mature software development methodologies (Agile, DevOps)
  • Implementing formal quality management systems
  • Continuous process improvement
  • Training and skill development
  • Knowledge sharing

2. Project-Level Strategies​

  • Clear requirements definition and management
  • Systematic architecture and design reviews
  • Formal change management
  • Regular status tracking and reporting
  • Risk management

3. Technical Strategies​

  • Test-driven development (TDD)
  • Continuous integration and delivery (CI/CD)
  • Automated testing at all levels
  • Static code analysis
  • Code reviews
  • Refactoring
  • Clean code practices

Trade-offs in Software Quality​

Quality attributes often have trade-offs, and improving one attribute might negatively impact another:

  • Performance vs. Maintainability: Highly optimized code may be harder to maintain
  • Security vs. Usability: Strong security measures might reduce ease of use
  • Time-to-market vs. Reliability: Rapid development might compromise reliability
  • Feature-richness vs. Simplicity: Adding features can increase complexity
  • Portability vs. Performance: Making software work across platforms may reduce performance on specific platforms

Conclusion​

Software quality is multifaceted, encompassing numerous attributes that contribute to the overall value and effectiveness of a software product. By understanding these attributes and their interrelationships, software engineers can make informed decisions about design, implementation, and testing strategies to achieve the desired level of quality.

The most effective approach to software quality considers the specific needs of stakeholders, the context in which the software will be used, and the constraints of the development process. By systematically addressing each relevant quality attribute through appropriate techniques and practices, development teams can create software that not only meets functional requirements but also provides a positive experience for users and long-term value for the organization.